internal: Fix sbt-airframe release (projectDotty); release 2026.2.2#4187
Merged
Conversation
The v2026.2.1 sbt-airframe release failed: its workflow published the airframe dependency libs via `projectJVM/publishLocal` on Scala 3, but projectJVM includes the Scala-2-only finagle module, which cannot compile on Scala 3. Use projectDotty (the Scala 3 JVM aggregate that excludes finagle) instead. The other release workflows succeeded at 2026.2.1 (Scala Native published), but since Central versions are immutable, cut a fresh 2026.2.2 for the complete, consistent suite. Validated the full sbt-airframe release chain locally (bootstrap -> projectDotty/publishLocal -> build sbt-airframe against the local 2026.2.2 libs). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the default SBT_AIRFRAME_VERSION from 2026.2.1 to 2026.2.2 across several files, including the GitHub Action bootstrap configuration, example projects, and the main project build plugin settings. I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
Tick the box to add this pull request to the merge queue (same as
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Follow-up to the
2026.2.1release attempt. The bootstrap fix worked (releases got past plugin resolution), but thesbt-airframerelease then failed:release-sbt-plugin.ymlbuilt the airframe dependency libs withprojectJVM/publishLocalon Scala 3, andprojectJVMincludes the Scala-2-onlyfinaglemodule, which can't compile on Scala 3 (98 errors).Fix: use
projectDotty(the Scala 3 JVM aggregate that excludes finagle) — a one-line change.Why a new version (
2026.2.2)Release Scala Nativefor2026.2.1completed and publishedairframe-*_native0.5_3:2026.2.1before the other jobs were cancelled. Central versions are immutable, so2026.2.1can't be reused for a complete release. Cutting2026.2.2gives one consistent version for the whole suite; the2026.2.0(airspec) and2026.2.1(native) partials remain harmless orphans (nothing depends on them — the main build pinsAIRSPEC_VERSION=24.12.1).Validation
Dry-ran the full sbt-airframe release chain locally (no Central):
publishLocalsbt-airframe2026.2.2(deps resolve from released24.12.1) — ✅projectDotty/publishLocal→airframe-*:2026.2.2, 0 errors, no finagle — ✅2026.2.2libs +publishLocal— ✅After merge
Tag
v2026.2.2→ all six release workflows publish the complete suite. Then remove the temporary CI + release bootstrap.🤖 Generated with Claude Code